SUPPORT / SAMPLES & SAS NOTES
 

Support

Problem Note 46413: ERROR: Libname is not assigned when attempting to update metadata for a SAS view

DetailsAboutRate It

If you attempt to update the SAS® Metadata Repository for a view using PROC METALIB or the Update Table Metadata feature in SAS® Management Console you will receive errors similar to the following:

ERROR: Libname MYLIB is not assigned. ERROR: SQL View _PMTA01_.MYVIEW could not be processed because at least one of the data sets, or views, referenced directly (or indirectly) by it could not be located, or opened successfully.

The errors occur because the libref that is used to reference the contributing data sets or views is stored with the view definition when the view is compiled. When the PROC METALIB executes, it assigns the view library using the reserved libref _PMTA01_. When PROC METALIB tries to open the underlying data set or view, it cannot because the libref stored within the view is not assigned.

You can circumvent the problem using one of the following methods:

  • explicitly add a LIBNAME statement to the application server's autoexec.sas file to ensure that the library is assigned using the libref that is stored in the view definition
  • include the USING LIBNAME clause in the definition for views created using PROC SQL to allow the library to be assigned using the necessary libref at execution time


Operating System and Release Information

Product FamilyProductSystemProduct ReleaseSAS Release
ReportedFixed*ReportedFixed*
SAS SystemBase SASWindows 7 Professional x649.21_M39.2 TS2M3
Windows 7 Home Premium x649.21_M39.2 TS2M3
Windows 7 Professional 32 bit9.21_M39.2 TS2M3
Windows 7 Home Premium 32 bit9.21_M39.2 TS2M3
Windows 7 Enterprise x649.21_M39.2 TS2M3
Microsoft Windows XP Professional9.21_M39.49.2 TS2M39.4 TS1M0
Windows 7 Enterprise 32 bit9.21_M39.2 TS2M3
Microsoft Windows Server 2008 for x649.21_M39.49.2 TS2M39.4 TS1M0
Microsoft Windows Server 20089.21_M39.49.2 TS2M39.4 TS1M0
Microsoft Windows Server 2003 for x649.21_M39.49.2 TS2M39.4 TS1M0
Microsoft Windows Server 2003 Standard Edition9.21_M39.49.2 TS2M39.4 TS1M0
Microsoft Windows Server 2003 Datacenter Edition9.21_M39.49.2 TS2M39.4 TS1M0
Microsoft Windows Server 2003 Enterprise Edition9.21_M39.49.2 TS2M39.4 TS1M0
Microsoft® Windows® for x649.21_M39.49.2 TS2M39.4 TS1M0
Microsoft Windows XP 64-bit Edition9.21_M39.49.2 TS2M39.4 TS1M0
Microsoft Windows Server 2003 Enterprise 64-bit Edition9.21_M39.49.2 TS2M39.4 TS1M0
Microsoft Windows Server 2003 Datacenter 64-bit Edition9.21_M39.49.2 TS2M39.4 TS1M0
z/OS9.21_M39.49.2 TS2M39.4 TS1M0
Microsoft® Windows® for 64-Bit Itanium-based Systems9.21_M39.49.2 TS2M39.4 TS1M0
Windows 7 Ultimate 32 bit9.21_M39.2 TS2M3
Windows 7 Ultimate x649.21_M39.2 TS2M3
Windows Vista9.21_M39.49.2 TS2M39.4 TS1M0
Windows Vista for x649.21_M39.49.2 TS2M39.4 TS1M0
64-bit Enabled AIX9.21_M39.49.2 TS2M39.4 TS1M0
64-bit Enabled HP-UX9.21_M39.49.2 TS2M39.4 TS1M0
64-bit Enabled Solaris9.21_M39.49.2 TS2M39.4 TS1M0
HP-UX IPF9.21_M39.49.2 TS2M39.4 TS1M0
Linux9.21_M39.49.2 TS2M39.4 TS1M0
Linux for x649.21_M39.49.2 TS2M39.4 TS1M0
OpenVMS on HP Integrity9.21_M39.49.2 TS2M39.4 TS1M0
Solaris for x649.21_M39.49.2 TS2M39.4 TS1M0
* For software releases that are not yet generally available, the Fixed Release is the software release in which the problem is planned to be fixed.